-
Notifications
You must be signed in to change notification settings - Fork 1.5k
new conf design — rate limit workaround #2016
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new conf design — rate limit workaround #2016
Conversation
@hasparus is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel. A member of the Team first needs to authorize it. |
run: | | ||
tsx scripts/sync-sched/sync.ts --year 2025 | ||
env: | ||
SCHED_ACCESS_TOKEN_2025: ${{ secrets.SCHED_ACCESS_TOKEN_2025 }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't really have this configured here so need @benjie to set this. (We have it over email thread or can share on slack)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can disregard it for now to unblock deploys. I ran the script locally, and this is a workflow_dispatch trigger. I'd prefer to run this on a webhook from Sched and maybe every N minutes (to avoid the rate limit), but we don't need it yet.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Closes #2014.
Description
We now pull the Sched's data to JSON files to avoid the 30req/min rate limit.
Preview on my Vercel account: fabulous-isomorphism-e22ige7yg-hasparus-projects.vercel.app